-
Notifications
You must be signed in to change notification settings - Fork 6.1k
Clarify that type abbreviations need not be shorter #50083
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Co-authored-by: BillWagner <[email protected]>
BillWagner
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This LGTM.
It's ready for final review.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR addresses issue #20495 by clarifying that F# type abbreviations can be shorter or longer than the original type name, despite the potentially misleading terminology. The change adds a NOTE block that explains common usage patterns and validates the use of longer, more descriptive names.
- Adds a NOTE block clarifying that type abbreviations can be any length
- Documents common usage patterns for the feature
- Preserves established terminology while addressing confusion
The term "type abbreviation" suggests the alternate name must be shorter, but the feature allows names of any length. All three examples in the doc actually show longer names, creating confusion.
Changes
The established "type abbreviation" terminology is preserved throughout F# ecosystem and tooling, so only a clarification note was added rather than renaming the feature.
Fixes #20495
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.
Internal previews